Partial retrieval of images in the compressed domain

ABSTRACT

In a method and a system for retrieving images in a client-server system, images are stored as a set of independently decodable units (CU&#39;s) on the server. A client issues a series of requests for image information. Each request contain a request number, information on what image information the client wants to see next and information on what image information the client had received at the time when the request was issued. The server does not have to store any state information (e.g. previous requests). On receiving a request, the server sends a restart marker, a confirmation of the request number and incremental image information corresponding to the request. The use of the method and the system as described herein will result in that no decoding of the whole bit stream will be required in the server. This will save a lot of time at the sender side (server side), since it not needs to a full decoding of the stream.

TECHNICAL FIELD

[0001] The present invention relates to a method and a system for transmitting images between a client and a server. The method and the system are particularly well suited for transmission of parts of images stored in a server.

BACKGROUND OF THE INVENTION AND PRIOR ART

[0002] Digital images can be stored on servers and distributed over a telecommunication network. Images can also be stored on physical media using for example a CD-ROM. If the image is large it might take some time to transmit the image. In order to speed up the transmission the client might select a region of the image that are more vital and then only receive the region. This is known as Region of Interest (ROI) coding.

[0003] In today's client-server systems, if a client wants to access an image from a server, a connection is established between the user program at the client side and the server. The user program then sends a request to get the desired image. The server reacts by fetching the file and starts the transmission. The user program can at any time send a new request to the server, e.g., a request for parts of a file. When the transmission is finished the connection is closed. Such a system is described in Fielding, et al, Hypertext Transfer Protocol—HTTP/1.1 rev 05, HTTP Working Group, INTERNET-DRAFT, Sep. 11, 1998 (Work in progress).

[0004] However, there is a problem with most of the still image compression techniques, like e.g. JPEG, in that they produce a bit stream being one inseparable coding unit. Thus, if a Region of Interest is selected the lack of independently decodable units forces the server to perform a complete decoding followed by a new encoding of the whole bit stream. Depending on the server software it sometimes even has to re-load the image from the storage media. The drawback with this is that a time consuming and computational complex scheme is required, which will put high demands on the computational power of the server.

[0005] Furthermore, in the emerging still image standard JPEG2000 independent entropy coding of so called coding units (CU) is used. A coding unit can for example be, a subband in the transform domain, in the case of i.e. wavelet transform), a part of a subband, such as bit plane or block of certain size (example 16×16), or a bit plane for a region within a subband.

SUMMARY

[0006] It is an object of the present invention to overcome the problems as outlined above and in particular to reduce the amount of processing and encoding in a server when a client requests an ROI or a part of the image.

[0007] This object and others are obtained by storing images as a set of independently decodable units (CU's) on a server. When a client requests a certain part of the image only information from the CUs that have not already been transmitted are then re-encoded, which saves a lot of processing time in the server.

[0008] For example, a client is issuing a series of requests for image information. Each request contain a request number, information on what image information the client wants to see next and information on what image information the client had received at the time when the request was issued. The server does not have to store any state information (e.g. previous requests). On receiving a request, the server sends a restart marker, a confirmation of the request number and incremental image information corresponding to the request.

[0009] The use of the method and the system as described herein will result in that no decoding of the whole bit stream will be required in the server. This will save a lot of time at the sender side (server side), since it not needs to perform a full decoding of the stream.

BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The present invention will now be described in more detail and with reference to the accompanying drawings, in which:

[0011]FIG. 1 shows the basic steps carried out in a client-server process.

[0012]FIG. 2 shows the steps carried out in a client-server process according to a first embodiment.

[0013]FIG. 3 shows the steps carried out in a client-server process according to a second embodiment.

[0014]FIG. 4 shows the steps carried out in a client-server process according to a third embodiment.

[0015]FIG. 5 shows the steps carried out in a client-server process according to a first alternative of the third embodiment.

[0016]FIG. 6 shows the steps carried out in a client-server process according to a second alternative of the third embodiment.

[0017]FIG. 7 shows the steps carried out in a client-server process according to a third alternative of the third embodiment.

[0018]FIG. 8 shows the steps carried out in a client-server process according to a fourth embodiment.

DETAILED DESCRIPTION

[0019] In FIG. 1, a basic interaction between a client and a server is shown. Thus first the client requests an image, step 101. Next in a step 103, the server starts to transmit the image to the client. The client then, at some time during transmission requests a portion of the image, which is currently being transmitted, step 105. The server then, in response to the request in step 105, starts to transmit the requested portion, step 107. The client may also request additional portions of the image at any time as indicated in step 109. The transmission can be interrupted at any time at a lower protocol level, such as TCP or HTTP.

[0020] In the following description and on the corresponding drawings the following definitions, syntax and notation is used:

[0021] A Coding Unit (CU) is a part of a bit stream that is independently decodable. Thus, it is possible to decode a certain part of the bit stream without having to decode the whole stream.

[0022] A TAG or re-sync mark is a combination of bits that can not be generated from the entropy encoder.

[0023] Syntax Elements in the Client-Server Process

[0024] Several detailed instances of a basic client server process are described below. They correspond to various specific formats of the syntax elements in the Client-Server process.

[0025] <Image data request> can have the following formats:

[0026] <Image data request 1>=send the first <number> subbands

[0027] <Image data request 2>=send the first <number> bit planes

[0028] <Image data request 3>=send the first <number> subbands of the ROI <ROI number> <ROI description>

[0029] <Image data request 4>=send the first <number> bitplanes of the ROI <ROI number> <ROI description>

[0030] <Image data request 5>=send <CU sequence> (describing what CU's are requested)

[0031] <Image data acknowledge> can have the following formats:

[0032] <Image data acknowledge 1>=<Image data acknowledge marker> bits/bytes/CUs received <number>

[0033] <Image data acknowledge 2>=<Image data acknowledge marker> CUs received <number> <CU n1> <CU n2> . . . <CU nn>, where <CU n> is the number assigned to a received CU

[0034] Version 1 is used with a re-sending and packet ordering transmission protocol such as TCP. Version 2 is used with a connectionless best-effort transmission protocol such as UDP.

[0035] <Image data > can have the following formats:

[0036] <Image data 1>=<CU stream> corresponding to the first <number> of remaining subbands

[0037] <Image data 2>=<CU stream> corresponding to the first <number> of remaining bit planes

[0038] <Image data 3>=<CU stream> corresponding to the first <number> remaining subbands of the ROI <ROI number>

[0039] <Image data 4>=<CU stream> corresponding to the first remaining <number> bit planes of the ROI <ROI number>

[0040] <Image data 5>=<CU stream> corresponding to the CU's specified in <Image data request 5>

[0041] Several different formats of <CU stream> are possible:

[0042] <CU stream 1>=<header> <Length CU1> <Length CU2> . . . <Length CUN> <CU1> <CU2> . . . <CUN>

[0043] <CU stream 2>=<header> <Length CU1> <CU1> <Length CU2> <CU2> . . . <Length CUN><CUN>

[0044] <CU stream 3>=<header> <Tag 1> <CU1<Tag2> CU2> . . . <Tag N><CUN>

[0045] <CU stream 4>=<header> <CU1> <Tag1> <CU2> <Tag 2> . . . <CUN> <Tag N>

[0046] The image header is not required is it already has been received by the client.

[0047] <Image transcoding header> contains a description of the transcoding operations that was performed on the original image in order to produce the transcoded image. The client use this information to map CU's from the original image to the transcoded image and to map CU's from the transcoded image to the original image.

[0048] <image posting notification> is used for telling the client that the transcoded image is stored at the server. It gives the URL of the transcoded image. A time-out can optionally be including indicated that the image will be saved only for a specified time.

[0049] In FIG. 2 a first embodiment of the present invention is shown. Thus, in this case the client wants to access parts of the stored image. This could be certain bit planes, subbands or pre-stored Regions of Interest. In this case the server do not use any special functions to respond to the request except the ones used in the communication protocol (e.g. HTTP). A process is for this is shown in FIG. 2.

[0050] Step 201, the client sends and requests for a stored image. The image is stored as a compressed bit stream and in a format comprising independently coded coding units (CU).

[0051] Step 203, the server responds and starts the transmission.

[0052] Step 205, the client decides that a part of the image is more important. The Client gets the information of where it is stored from the image header, and sends a request to the Server for the desired part. The part can be an ROI or image data, which increases the quality of the whole image.

[0053] Step 207, the Server may now send a re-start mark and starts the transmission of the wanted CU's.

[0054] The re-start marker functionality can also be provided by a lower protocol in the stack, e.g. TCP or HTTP. The re-start marker can optionally be excluded if it can be derived from information in the lower protocol levels.

[0055] In FIG. 3 another type of client server process is shown. In the process shown in Fig. 3, no advanced processing is performed at the server side. In the example described in conjunction with FIG. 3, a Client starts receiving an image and then in the middle of the transmission decides that some part of the image is more vital and only want that part to be transmitted. This could be a number of bit planes, subbands or Regions of Interest. It should be noted that in this case the image could be stored with a Region of Interest (ROI) but the user wants to select another ROI.

[0056] In such a case the server has to use some additional functions for finding the requested parts of the compressed image. The interaction between the Client and the Server and the operation at each sides can then be as follows, acknowledgement messages and similar massages are not shown for clarity reasons. The can for example use IP, TCP/UDP, HTTP or similar protocols for such messages.

[0057] Step 301, a client sends and requests for a stored image. The image is stored as a compressed bit stream and in a format having independently coded coding units (CU).

[0058] Step 303, the Server responds and starts the transmission

[0059] Step 305, the Client decides that a part of the image is more important and if a Region of Interest is selected it also sends the shape of the selected region and some other information needed. This could be, e.g., the chronological number of the request, the number of CU's or bytes received, marked with (*) in FIG. 4. At this point the Client has created a mask in the transform domain, for example using the method described in Charilaos Christopoulos (editor), JPEG 2000 Verification Model Version 1.2, ISO/IEC JTC1/SC29/WG1 N982, Aug. 14, 1998, that selects the coefficients needed for the server to decide what CU's are needed from the Server.

[0060] Step 307, the Server gets the request. The server uses information in the bit stream, such as TAGS, in order to find the desired CU's. The server now sends a re-start mark and if needed the lengths of the remaining CU's. It then starts the transmission of the requested CU's.

[0061] In the following the situation where a Client starts receiving an image and then in the middle of the transmission decides that some part of the image is more vital and only want that part to be transmitted is dealt with. This is also known as selection of Region of Interest. It should be noted that in this case the image could be stored with a Region of Interest (ROI) but the user wants to select another ROI. In the example below the JPEG2000 progressive-by-resolution (PBR) scheme is used. A similar method can however be applied in progressive-by-accuracy (PBA) schemes, as is described in Charilaos Christopoulos (editor), JPEG 2000 Verification Model Version 1.2, ISO/IEC JTC1/SC29/WG1 N982, Aug. 14, 1998.

[0062] In FIG. 4, the progressive-by-resolution scheme in JPEG2000, is shown. In the PBR mode of JPEG2000 each subband can, in a simplified way, be viewed as a coding unit, CU, since the whole subband is independently entropy coded. This is the case if the so called non-adaptive mode is used, since in this case a subband is the same thing as a sequence. This will make it possible to entropy decode any subband independently if the Client knows where to find it in the bit stream. In the very basic mode of JPEG2000 this is supported by an array, that is stored in the image header, containing the lengths of each CU in bits/bytes. Thus it is possible for the Client to parse the bit stream since it knows the length of each entropy-coded subband.

[0063] The client sends a request to a server and requesting a stored image. The image is stored as a compressed bit stream. The server gets the bit stream and starts the transmission.

[0064] In a preferred embodiment, the interaction between the Client and the Server and the operation at each sides is as follows, acknowledgement messages and similar messages are left out for reasons of clarity.

[0065] First the client sends and requests for a stored image. The image is stored as a compressed bit stream and in a CU format.

[0066] The Server then responds and starts the transmission

[0067] At some point during the transmission, the Client decides that a part of the image is more important and sends the shape of the selected region and some other information needed. This can, e.g., be the chronological number of the request, the number of CU's or bytes received, marked with (*) in FIG. 4.

[0068] The Server then gets the request for the ROI and performs an entropy decoding for the CU's that has not been sent. In this case it is the subbands that not have been sent yet. The entropy decoding will give the quantized transform coefficients. The server creates a mask in the transform domain. Then the server can select the coefficients that are needed for the Region of Interest, for example using the method described in Charilaos Christopoulos (editor), JPEG 2000 Verification Model Version 1.2, ISO/IEC JTC1/SC29/WG1 N982, Aug. 14, 1998. Thus, by using the mask the Server selects which coefficients are needed in each of the remaining subbands. The quantized coefficients belonging to the Region of Interest are then entropy encoded subband wise. Thus, the same CU structure is kept. The Server may now send a re-start mark and the lengths of the CU's to be sent and starts the transmission of the CU's.

[0069] The Client gets the response from the server describing what type of transcoding that have been used. The Client then creates the desired mask in the transform domain, for example using the method described in Charilaos Christopoulos (editor), JPEG 2000 Verification Model Version 1.2, ISO/IEC JTC1/SC29/WG1 N982, Aug. 14, 1998 that selects the coefficients needed for the response from the Server.

[0070] From the Client point of view the result will be that the Region of Interest will have full resolution, while the background will have a reduced resolution (which could improve in later stages if the method described above using the shifting is used). The amount of reduction of course depends on when the Region of Interest request was done.

[0071] If the request for the Region of Interest hits in the middle of a CU, which will be the most probable case, there are two ways of proceeding. Either the CU where the request hit is re-transmitted, or the transmission of the CU is completed and then the re-coding starts.

[0072] In the case of the progressive-by-accuracy mode in JPEG2000 the same idea as in the previous example can be used without any major changes. In this case a CU is a bit plane. Thus, the bit stream is ordered by accuracy. First the highest bit plane is transmitted and then the second highest and so on.

[0073] The interaction between the Client and the Server and the operation at each sides are the following, where acknowledgement messages and similar messages are left out.

[0074] First the client sends and requests for a stored image. The image is stored as a compressed bit stream and in CU format.

[0075] The Server responds and starts the transmission.

[0076] The Client decides that a part of the image is more important and sends the shape of the selected region and some other information needed. This could, e.g., be the chronological number of the request, the number of CU's or bytes received, marked with (*) in FIG. 4. At this point the Client has created a mask in the transform domain, for example using the method described in Charilaos Christopoulos (editor), JPEG 2000 Verification Model Version 1.2, ISO/IEC JTC1/SC29/WG1 N982, Aug. 14, 1998, that selects the coefficients needed for the response from the Server.

[0077] The Server gets the request for the ROI and performs an entropy decoding for the CU's that has not been sent. In this case it is the bit planes that not have been sent yet. The entropy decoding will give the remaining parts of the quantized transform coefficients. The server creates a mask in the transform domain. Then the server can select the coefficients that are needed for the Region of Interest, for example using the method described in Charilaos Christopoulos (editor), JPEG 2000 Verification Model Version 1.2, ISO/IEC JTC1/SC29/WG1 N982, Aug. 14, 1998. Thus, by using the mask the Server selects which coefficients are needed in each of the bit planes. The remaining parts of the quantized coefficients belonging to the Region of Interest are then entropy encoded bit plane wise. Thus, the same CU structure is kept. The Server can now send a re-start mark and the lengths of the CU's to be sent and starts the transmission of the CU's.

[0078] Instead of having a reduction of the resolution in the background, as in the previous example, the accuracy of the pixels not belonging to the Region of Interest is reduced. This is done by simply skipping the remaining bit planes for bit planes belonging to the background.

[0079] On receiving a request, the server transcodes the original image. The transcoded image is either sent to an output buffer, processes C1 and C2 below or posted as a new image, process C3 below. A new client request will always refer to a posted image either the original image as in C1 and C2, see below, or the posted transcoded image as in C3, see below. The client is responsible for transforming between image formats so that received image information referring to the original image can be reused in the client's copy of the transcoded image. Successful reuse is reported to the server in <Image data acknowledge> messages.

[0080] Client-Server Process C1 (Optimized for Download Speed)

[0081] This process could start without any previous transfer of image information. A client-server process according to cases described above in conjunction with FIGS. 2 or 3, might, however, have occurred. Some of the CUs of the original image might have been transferred to the client during this process. The client knows about this previous activity but the server does not store any such state information.

[0082] Client request 1) <request number> <Image data acknowledge> <Image data request>

[0083] Server response 1) <restart marker> <request number> <image transcoding header> <image header> <CU stream> (the header of the transcoded image is sent)

[0084] If the client does not understand the new format, it can interrupt the stream at the TCP level. A new set of client-server exchanges can continue. They will always refer to the original image since the transcoded image usually is not kept by the server. If a new request according to case occurs, the server will then usually repeat the transcoding operation. The server might decide to save a cached copy of the transcoded image but this cannot be assumed by the client.

[0085] Client-Server Process 2 (Optimized for Low Bandwidth)

[0086] This process can also start without any previous transfer of image information. A client-server process according to cases described above in conjunction with FIGS. 2 or 3, might, however, have occurred. Some of the CUs of the original image might have been transferred to the client during this process. The client knows about this previous activity but the server does not store any such state information.

[0087] Client request 1) <request number> <Image data acknowledge> <Image data request>

[0088] Server response 1) <restart marker> <request number> <image transcoding header> <image header> (the server has only calculated the header of the transcoded image. A complete transcoding has not been performed)

[0089] Client request 2) <request number> <Image header acknowledge> <Image data acknowledge> <Image data request> (The client confirms that it can handle the transcoded format. The request is repeated since the server does not save the old request)

[0090] Server response 2) <restart marker> <request number> <CU stream> (the server performs a complete transcoding and sends the body of the image file to the output buffer)

[0091] Client-Server Process C3 (a Transcoded Image is Posted by the Server)

[0092] This process could start without any previous transfer of image information. A client-server process according to cases described above in conjunction to the FIGS. 2 or 3 might, however, have occurred. Some of the CUs of the original image might have been transferred to the client during this process. The client knows about this previous activity but the server does not store any such state information.

[0093] Client request 1) <request number> <Image data acknowledge> <Image data request>

[0094] Server response 1) <restart marker> <request number> <image transcoding header> <image header> <image posting notification>

[0095] Client request 2) (the client is now addressing the posted transcoded image at the http protocol level) <request number> <Image header acknowledge> <Image data acknowledge> <Image data request>

[0096] (The client is responsible for transforming CUs from the original image to the format of the transcoded image. The result of these operations is put in the <Image data acknowledge>)

[0097] Server response 2) <restart marker> <request number> <CU stream>

[0098] A new set of client-server exchanges can continue. They can refer to the original or transcoded image according to decisions by the client.

[0099] It should be noted that in some situations the number of received CU's or bits/bytes is not needed. This is the case if the Client continues to receive image data after the request(s) has been sent. The Server sends the re-start mark and maybe some other info in order to inform the Client that from now on the requested bit plane, subband or Region of Interest is coming.

[0100] Below additional examples of interactive selection of Regions of Interest during transmission from bit streams when the stream does not contain the desired Region of Interest are described. The examples illustrates the different bit stream formats <CU stream 1>-<CU stream 4>

[0101] Above, in conjunction with FIG. 4, the PBR-mode of the JPEG2000 coder is described. A modification of the scheme described above would be to send the length of the CU together with the data. Thus, when the Server gets the request for the ROI and performs an entropy decoding for the CU's that has not been sent. Instead of sending a re-start mark and the lengths of the CU's to be sent and starts the transmission of the CU's, the Server can now send a re-start mark and the length of the following CU.

[0102] The resulting Client-Server process is shown in FIG. 5. This will result in that there is no need to re-send the array of CU lengths as shown in FIG. 4.

[0103] It is also possible to use TAGS or re-sync marks in the bit stream. Thus instead of having an array describing the length of each CU above in conjunction with FIG. 4, the CU can be marked out in the bit stream by a bit pattern that is not generated by the entropy coder. The bit stream is searched in a sequential manner in order to find the different coding units.

[0104] The interaction between the Client and the Server and the operation at each sides is changed so that instead of sending a re-start mark and the lengths of the CU's to be sent and starts the transmission of the CU's, the Server can send a re-start mark and a TAG before the corresponding CU. The resulting Client-Server process is shown in FIG. 6.

[0105] It should be noted that an alternative way is to use send the TAGS after each CU or header instead of before the CU as is shown in FIG. 7. Thus, the interaction between the Client and the Server and the operation at each sides is changed so that instead of sending a re-start mark and the lengths of the CU's to be sent and starts the transmission of the CU's, the Server sends a re-start mark and a TAG after the corresponding CU.

[0106] Another solution could be to use the “scaling based method” in JPEG2000 for the rest of the subbands. This means that the ROI mask for the remaining subbands still is produced, but no different encoding of the ROI mask coefficients must be performed. The ROI mask coefficients are scaled up by a certain factor. Then encoding of the subbands will continue without changes. The shifting value must be stored in the bit stream, so the Client can shift down. Thus, the interaction between the Client and the Server and the operation at each sides is changed so that instead of sending a re-start mark and the lengths of the CU's to be sent and starts the transmission of the CU's, the Server can now send a re-start mark and a TAG after the corresponding CU.

[0107] In the schemes described above in conjunction with FIGS. 4-7, the Server needs to perform an entropy decode and then an entropy encode of the quantized coefficients. This is not so good if a really fast access of different parts of the image is desired.

[0108] The solution to this problem is that the image is divided into blocks that are independently decodable. These will be the CU's. The interaction between the Client and the Server and the operation at each sides are the following is shown in FIG. 8. It should be noted that acknowledgement messages and similar messages are left out.

[0109] Step 801, The client sends and requests for a stored image. The image is stored as a compressed bit stream.

[0110] Step 803, The Server responds and starts the transmission

[0111] Step 805, The Client decides that a part of the image is more important and creates a mask in the transform domain, see Ref. 1, that selects the CU's needed. The desired CU's is sent to the Server.

[0112] Step 807, The Server gets the request for the CU's. The Server may now send a re-start mark and the TAG for is before its corresponding CU.

[0113] The method and system as described herein provides a number of advantages compared with prior client-server systems for retrieving images. Thus, the Server does not need any memory to store information of what parts it has sent. In the first embodiment the server does not need to perform any processing whatsoever in order to give the client the wanted desired parts of the bit stream. The Client will get the information of where the requested parts are stored from the image header. In the first and second embodiment, the Server does not need to perform any entropy decoding, it only has to send the requested CU's. Thus, decreasing the transmission time dramatically. In the third embodiment the Server does not have to decode that whole bit stream. This will save a lot of time at the sender side (server side), since it not needs to a full decoding of the stream.

[0114] The method and system as described herein can also be extended to be used together with a video compression algorithm that have independent decodable units in the compressed video stream. 

1. A method of transmitting an image, which is stored as a number of independently decodable coding units, between a server and a client, characterized by the steps of: transmitting a request for image data from the client to the server, starting transmission of the requested image data from the server to the client, transmitting a request for a new part of the image during or after transmission thereof, and transmitting the requested new part of the image from the server to the client using only coding units not already transmitted.
 2. A method according to claim 1, characterized in that the image is stored in the transform domain.
 3. A method according to any of claims 1-2, characterized in that each request from the client comprises a request number.
 4. A method according to any of claims 1-3, characterized in that each request from the client comprises information on which image information the client is interested in and which information about the image the client already has access to.
 5. A method according to any of claims 1-4, characterized in that the server after having transmitted requested information to the client directly discards all information provided by client.
 6. A method according to any of claims 1-5, characterized in that the server transmits a marker code prior to transmitting requested coding units.
 7. A method according to any of claims 1-6, characterized in that the server performs a transcoding before transmitting the new image part.
 8. A client-server system, wherein images are stored as a number of coding units in the server, characterized by: means in the server for receiving a request for image data from the client, means for transmitting the requested image data from the server to the client, means in the server for receiving a request for a new part of the image during or after transmission thereof, and means in the server for transmitting the requested new part of the image from the server to the client using only coding units not already transmitted.
 9. A system according to claim 8, characterized by means for storing the images in the transform domain.
 10. A system according to any of claims 8-9, characterized in that each request from the client comprises a request number.
 11. A system according to any of claims 8-10, characterized in that each request from the client comprises information on which image information the client is interested in and which information about the image the client already has access to.
 12. A system according to any of claims 8-11, characterized in that the server is arranged to directly discards all information provided by client after having processed it.
 13. A system according to any of claims 8-12, characterized in that the server is arranged to transmits a marker code prior to transmitting requested coding units.
 14. A system according to any of claims 8-13, characterized in that the server is arranged to perform a transcoding of the coding units not already transmitted before transmitting the new image part. 